feat: connect new backend conversation with frontend #182
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
error9098x
commented
Nov 6, 2025
error9098x
commented
- changes the existing structure to support the new FastAPI endpoints with the server-side conversational threads.
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR refactors the chat interface to migrate from a client-side sessionStorage-based chat thread system to a backend API-driven conversation management system. The changes introduce proper conversation persistence, improved message structure, and better source handling.
- Replaces local thread storage with server-side conversation management via REST APIs
- Refactors message structure from question/answer pairs to role-based chat messages
- Implements optimistic UI updates for better user experience
- Adds URL extraction from context sources when explicit source URLs are missing
Reviewed Changes
Copilot reviewed 4 out of 6 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
frontend/nextjs-frontend/components/SourceList.tsx |
Updated to handle ContextSource objects and extract URLs from context text when source is unavailable |
frontend/nextjs-frontend/components/MessageList.tsx |
Refactored to display role-based messages with proper user/assistant UI distinction |
frontend/nextjs-frontend/components/ChatHistory.tsx |
Renamed thread terminology to conversations and added active conversation highlighting |
frontend/nextjs-frontend/app/page.tsx |
Major refactor to integrate backend conversation APIs, implement CRUD operations, and add proper error handling |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
error9098x
force-pushed
the
frontend-db
branch
2 times, most recently
from
30fb822 to
1d2a61d
Compare
Collaborator
|
@error9098x Is there a way you can test this PR independently of #181? |
Signed-off-by: error9098x <[email protected]>
Signed-off-by: Jack Luar <[email protected]>
Signed-off-by: Jack Luar <[email protected]>
Signed-off-by: Jack Luar <[email protected]>
Signed-off-by: Jack Luar <[email protected]>
- backend: order messages by created_at - fix conversations payload Signed-off-by: Jack Luar <[email protected]>
Signed-off-by: Jack Luar <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.